Release 10.1A: OpenEdge Application Server:
Administration


Summary of management tasks

This section summarize the basic management tasks that are available to maintain existing AppServer configurations. They are described with reference to the command-line utilities, but you can also accomplish most of these tasks, except running the AdminServer, using the Progress Explorer.

Table 2–4 describes the utilities (in addition to the Progress Explorer tool) that OpenEdge provides to help configure and manage an AppServer installation, listed generally in order by task.

Table 2–4: AppServer utilities 
Utility
Execution location
Description
ASBMAN 
Local or remote to the AppServer installation.
Starts, stops, adds AppServer agents, trims AppServer agents, and queries status for an AppServer instance and its AppServer agent.
ASCONFIG 
Local to the AppServer installation files.
Validates the syntax of AppServer configurations in the ubroker.properties file. (Never needed if you always use the Progress Explorer GUI.)
NSCONFIG 
Local to the AppServer installation files.
Validates the syntax of NameServer configurations in the ubroker.properties file. (Never needed if you always use the Progress Explorer GUI.)
NSMAN 
Local or remote to the NameServer machine.
Starts, stops, and queries status for a NameServer.
PROADSV 
Local to the AppServer installation.
Starts, stops, and queries status for the AdminServer on UNIX. In Windows, you start the AdminService as a Windows service using the Services applet in the Control Panel.

For more information on the NameServer and NSMAN utility, and the AdminServer and PROADSV utility, see the "NSMAN" section, the "PROADSV" section, OpenEdge Getting Started: Installation and Configuration .

Table 2–5 lists sample command-line utility syntax used to:


Copyright © 2005 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095